Apparatus of mapping logical point-of-delivery to physical point-of-delivery based on telecommunication information networking

ABSTRACT

The present invention discloses an apparatus of mapping logical point-of-delivery to physical point-of-delivery, which is capable of maintaining the completeness and consistency of each project&#39;s point-of-delivery environment within a corporate data center by utilizing session mechanisms in each layer of the TINA-variation architecture. The apparatus of the present invention is based on a new TINA-variation architecture, which vertically includes four session layers: Access Session Layer, Service Session Layer, Resource Session Layer, and Provision Session Layer. Resource Session Layer and Provision Session Layer are among the innovative features of the present invention. The service target of the new architecture is enterprise data center. The new architecture is left-right asymmetrical; it horizontally includes Project Developer Domain, Resource Provision Domain, and Application User Domain. The resources it involves are extended from network connection resource covered by standard TINA, to all assets under management in enterprise data center, including network, storage, and computing resources.

CROSS REFERENCE TO RELATED APPLICATION

This application is the national phase under 35 USC 371 of internationalapplication no. PCT/CN2012/081106, filed Sep. 7, 2012. The contents ofthe aforementioned applications are incorporated herein in theirentirety.

FIELD OF THE INVENTION

The present invention relates to a mapping apparatus, which leveragesTINA (Telecommunication Information Networking Architecture, originsfrom the telecommunication service industry) and then modifies andadjusts it into a new TINA-variation architecture. The new architectureis applicable to the cloud computing resource management, and no longersuitable to the telecommunication service industry where TINA originsfrom. Specifically, this novel TINA-variation architecture ishorizontally asymmetrical, and has four session layers vertically. Whilework together, they can map logical point-of-delivery to physicalpoint-of-delivery. With session mechanisms, the architecture is capableof maintaining the completeness and consistency of each project'spoint-of-delivery environment within a corporate data center after themapping process.

BACKGROUND

From a common user's viewpoint, cloud computing offers “unlimited”computing, storage, and network capacities. However, providing“unlimited” capacities is neither practical nor attainable. In fact,suppliers must be able to build their infrastructure in a linear andconsistent way to meet cloud users' growing infrastructure demand andoptimize the usage. This linear growth can be achieved throughpoint-of-delivery. A point-of-delivery is “a network service modulecomposed of network, computing, storage, and application components”. Itis also a design pattern which can be implemented and duplicated tomaximize modularity, scalability, and manageability of a data center.The difference between point-of-delivery and the other design patternsis that it is a deployable module. This module provides “services”, andall components inside the module share one and the same failure domain.In other words, if a failure occurs inside one point-of-delivery, it mayonly affect the projects within the point-of-delivery, and will notaffect the projects outside the point-of-delivery.

The concept of point-of-delivery was first proposed by Cisco. Itrepresents a type of fast-deployable, fast-deliverable constructionmodule, which includes the technologies of service, security,networking, management, software virtualization, and data centerinterconnection. A point-of-delivery can be constructed throughdifferent types of ways. First of all it shall have a definition, namelya point-of-delivery is a duplicable physical environment, includingcomputing, network, and application resources, etc. The most importantfeature of a point-of-delivery is all virtualized applications canmigrate freely within it, avoiding so-called the routing-layer obstacle.For different users, point-of-delivery designs may vary, it may includeall aggregation switches under a core switch inside a data center; itmay be a little smaller in scale. In the former case, the entire systemmay achieve higher efficiency; applications can acquire resources to runfreely inside a larger cluster of computers, but certainly the designitself is not very flexible. If a point-of-delivery needs 2,000square-meter rooms, then a 1,000 square-meter room next to it will notbe utilized. In the latter case, a relatively small point-of-deliverywill be more flexible, but resource utilization efficiency will not govery high, since the resource scheduling is only operated in a smallscale. Point-of-delivery provided by service provider's infrastructureis particularly important, for example: in a cloud computing servicesupported data center, point-of-delivery can help it to maintainscalability while its workloads/data volume is increasing.

The main objective of the present invention is to improve resourceutilization efficiency by dynamically scheduling resources withinsmall-scale point-of-delivery. In the present invention,point-of-delivery can be classified as logical one or physical one.Logical point-of-delivery refers to the combination of logical resourcesof computing, network, and storage that user's business projectrequired. They are “subscribed” through user's specification, accordingto which the resources can be shared by space or by time. Physicalpoint-of-delivery is a physical provisioning unit of datacenter networkequipment through a set of resource definition and classification. Theunit can work independently, and is considered as deliverable unit ofresource services. That means, the basic unit of resource provisioning,is not a single physical server, a virtual server or a virtual switch,but a (meaningful) “set” of these resources. Here is a metaphor todescribe the relationship between logical and physicalpoint-of-delivery: a logical point-of-delivery is like booking a Chinesewedding banquet, the specification of which includes how many roundtables for the wedding banquet, how many seats for each table, as wellas how many dishes for each table, etc; the physical point-of-deliveryis the actual wedding banquet where the guests and hosts enjoy thefeast. The term point-of-delivery defined by Cisco actually refers tothe physical point-of-delivery only. The distinction between logical andphysical point-of-delivery, particularly the process of mapping thelogical point-of-delivery to physical point-of-delivery is one of themajor contributions of the present invention.

It's noteworthy that logical point-of-delivery has following features:

(1) A logical point-of-delivery often contains multiple “virtualservers”. “Virtual Server” means server virtualization or abstraction ofa physical server, which is considered as a type of logical resource.Virtual servers are allowed to over-subscribe a physical (host) serverby sharing its space or time. Software running on a physical host serverto achieve space or time sharing is called “hypervisor”. On a physicalhost server, each virtual server has its own hardware specification, andruns independent of each other. Physical host server is invisible notonly to provisioning instances of logical point-of-delivery, but alsoapplication users.

(2) Besides virtual server's hardware specification can be provisionedon-demand, virtual server's operating system can also be provisionedon-demand.

(3) Besides virtual server's operating system can be provisionedon-demand, application server (software) can also be provisionedon-demand on each over-subscribed operating system.

The present invention focuses on (1). The relationship between logicaland physical resources can be summarized as following: from a businessproject to a logical point-of-delivery is a one-to-one mapping process;from logical point-of-delivery to physical point-of-delivery is amultiple-to-multiple mapping process. By subscribing the logicalresources in a logical point-of-delivery, a project developer thus infurther subscribes distributed physical resources of the physicalpoint-of-delivery.

There are eight related patents listed below. Through briefintroductions and comparison, the present invention displays novelty andcreativity in following two aspects: distinguishing logicalpoint-of-delivery from physical point-of-delivery, and proposing themethod of mapping logical point-of-delivery to physicalpoint-of-delivery; with session mechanisms, it is capable of maintainingthe completeness and consistency of each project's point-of-deliveryenvironment after the mapping processes.

(1) patent CN101398768A “Construct Method of Distributed Virtual MachineMonitor System”, by using the “latest” virtualization technology betweenhardware and operating system, deploys and constructs distributedvirtual machine monitor system DVMM on multiple physical nodes. DVMMconsolidates and virtualizes multiple computer resources and turns theminto virtual resources, and unifies the management of these resources.According to application requirements, it can either integrate multiplecomputer resources into a single virtual machine in order to meet theresource requirements of some super computation task; or create multiplevirtual machines on one computer to consolidate multiple small-scaleapplications onto a single machine, in order to improve resourceutilization efficiency. This patent only involves server (i.e. computingresource) virtualization, but not concerns with storage resource andnetwork resource virtualization. And the system structure is relativelysimple.

(2) Patent CN101938416A “Cloud Computing Resource Scheduling MethodBased on Dynamic Reconfiguration of Virtual Resources”, according to theloading information of the cloud applications collected by cloudapplication monitor, is able to dynamically reconfigure virtualresources, based on the loading capacity of the virtual resources andcurrent loading volume of the cloud applications.

(3) Patent CN102170474A “Dynamic Scheduling Method and System forVirtual Resources in the Cloud Computing Network”, uses a live migrationmethod to achieve dynamic virtual resource scheduling, dynamic loadbalancing, and high utilization efficiency of virtual resources througheffective load balancing.

The “virtual resources” in Patent (2) and (3) only refer to virtualmachines; and the “physical resources” refers to related CPU, memory,and storage (disks). While these two patents concern with virtualresource scheduling, virtual resources being scheduled only refer tocomputing resources, and do not involve storage and network resources.

(4) Patent CN102291445A “Cloud Computing Management System Based onVirtualized Resources”, by using B/S (Brower/Server) architecture andvirtual machine technology, allows user to rent virtual machineson-demand through self-service at any place any time. It supportscustomized configuration of virtual machines, and helps user to useresources more effectively.

The virtual resources in Patent (4) include underlying virtual resourcepool, virtual machine management modules, virtual machine servermodules, and virtual machine storage modules. The patent involves server(computing resource) and storage resource virtualization, but notnetwork resource virtualization.

(5) Patent US20080082983A1 “Method and System for Provisioning ofResources” contemplates a method of autonomous provisioning of resourcesof a computer system, wherein performance-critical workload of thecomputer system is monitored; workload suffering is detected based oncomparing the performance-critical workload with defined values ofperformance-critical workload goals; types of missing resources aredetermined; additional resources available for activation aredetermined; the additional resources are activated, and a notificationof the activation is generated for being sent to a system provider, e.g.for automated billing of the added capacity.

Patent (5) includes “(optional) virtual hardware platform.” The virtualhardware platform only refers to virtual machines (see FIG. 1 of patentUS 20080082983A1). As the virtual hardware platform is “optional”, whichmeans the system is able to work properly without virtual machines,virtualization is not the critical technology to achieve autonomousprovisioning of resources of a computer system. Obviously it is quitedifferent from the present invention, which uses virtualization as thekey technology for mapping logical point-of-delivery to physicalpoint-of-delivery.

(6) Patent CN102292698A and Patent US20100198972A1 basically have thesame content: “Methods and Systems for Automated Management of VirtualResources in a Cloud Computing Environment”. The applicant of these twopatents is Citrix Systems Inc. They describe a virtual resourcesmanagement system in cloud computing environments, including a hostcomputing device communication component and a storage systemcommunication component. The storage system communication component isexecuted by a storage delivery management service, communicates with astorage system adapter in a storage area network to identify a storagesystem in a storage area network, and directs the automated provisioningof a virtual storage resource on the identified storage system.

The “virtual resources” in Patent (6) refer to virtual storage resourcesonly, and do not include computing resources and network resources inthe cloud computing environment. The present invention involves themanagement of computing, storage, and network resources, which is quitedifferent from Patent (6).

In brief, the main difference between the present invention and Patent(1)-(6) lies in the following three aspects:

-   1) The present invention not only involves the computing resource    (server) virtualization, but also storage resource and network    resource virtualization.-   2) The present invention does not manage resources by the unit of    single physical resource or virtual resource, but orchestrates the    computing, storage, and network resources with unified scheduling    based on the unit of point-of-delivery.-   3) The objective of the present invention is how to maintain the    completeness and consistency of each project's point-of-delivery    environment within a corporate data center during the processes of    mapping the logical point-of-delivery to the physical    point-of-delivery; rather than focusing on the details of mapping    process (that's beyond the scope of the present invention).

(7) Patent CN102347959A “System and Method of Resource Access SystemBased on Identity and Session”. The main objective is maintaining theidentities of resource, service provider, session, and applicationduring the resource access processes by session mechanisms.

Based on Patent (7), the present invention clarifies the relationshipsbetween various sessions, and proposes a new TINA-variation four-layerarchitecture, which uses session mechanisms to maintain the integrityand consistency of the point-of-delivery environments.

(8) Patent EP1091599A1 “Method for Accessing a Service Platform Such AsTINA via an Internet Browser Session” describes the method of accessinga service platform such as TINA through an Internet browser session.With TINA service platform and the session mechanisms of TINA, itprovides the mean to identify bilaterally the service provider and theservice consumers and users, and a consistent way to identify a user,and provide the ability to subscribe, tailor, manage, and/or account hispreferred services. In the end the user may access the service sessionvia the browser session.

The concepts of service provider, service consumer, and user in Patent(8) are limited to the field of Internet. The TINA-variationarchitecture described by the present invention is applied to the cloudcomputing resource management in a corporate data center. The servicetarget of the architecture is not simple B/S (Brower/Server)architecture systems anymore, but a variety of cloud computingresources, which is a big difference. The TINA architecture has beenmodified to a great extent; please see following sections for thedetails.

SUMMARY

As the goals mentioned above, the embodiment of the present invention isa service delivery platform, which is able to map logicalpoint-of-delivery to physical point-of-delivery. It is capable ofmaintaining the completeness and consistency of each project'spoint-of-delivery environment within a corporate data center byutilizing session mechanisms in each layer of the TINA-variationarchitecture

The technology solution of the present invention is as follows. Thepresent invention discloses an apparatus of mapping logicalpoint-of-delivery to physical point-of-delivery for cloud computingresource management in an enterprise data center. The embodiment of theapparatus is a service delivery platform. The apparatus is based on anew TINA-variation architecture. The service target of theTINA-variation architecture is enterprise data center. TheTINA-variation architecture vertically includes Access Session Layer,Service Session Layer, Resource Session Layer, and Provision SessionLayer. The TINA-variation architecture is left-right asymmetrical. Theresources of the TINA-variation architecture are IT resource, storageresource, and network resource. The service delivery platform mentionedabove is used by project developer, project operator, application user,and system operator. The service delivery platform includes:

Project Delivery Service Network: includes Project Core Service, ProjectDesign Service, Project Delivery Scheduling, and Project SubscriptionService;

Project Logical Environment Service Network: in which theproject-delivery-and-scheduling function supports automatic or manualoffline-online environment switching, and supports scheduling multiplesets of project's point-of-delivery. Project Logical Environment ServiceNetwork includes multiple sets of offline-project's and online-project'slogical point-of-delivery.

Project Logical Environment Storage Network: includes multiple sets ofoffline-project instance's point-of-delivery;

Project Logical Environment Resource Network: includes multiple sets ofonline-project instance's point-of-delivery;

Virtual Resource Network: in which virtual resources aggregate physicalresources of different configurations and different locations, toachieve resource consolidation regardless of types and deployments ofthe physical resources. Including unallocated and allocated virtualresources, Virtual Resource Network provides support (functions) ofexclusive holding or sharing virtual resources.

Data Center Physical Resource Service Network Divided by Project:includes multiple sets of physical point-of-delivery. The Data CenterPhysical Resource Service Network Divided by Project supportssubscription and commitment (i.e., delivery) of point-of-delivery, andsupports sharing physical resources by space or by time. Data CenterPhysical Resource Service Network Divided by Project includesunallocated and allocated physical resources.

In one embodiment of the present invention, an apparatus of mapping thelogical point-of-delivery to the physical point-of-delivery is provided,wherein the TINA-variation architecture includes several session-relatedservice components in the service delivery platform. These servicecomponents are distributed in Project Development Domain, ResourceProvision Domain, and Application User Domain. Project DevelopmentDomain and Application User Domain contain all instantiated componentsat developer/operator/user terminal. Resource Provision Domain containsall instantiated components and resources at one or several resourceprovision points in the network.

In one embodiment of the present invention, an apparatus of mapping thelogical point-of-delivery to the physical point-of-delivery is provided,wherein the Access Session Layer includes following access sessionrelated components:

An Access Session Developer-Operator (component): is used to create anew session; in the session, the project developer plans a logicalpoint-of-delivery, while he/she obtains the project-specific resourcerequirements. The project operator schedules the activate time, themoment when the project's logical point-of-delivery maps to the physicalpoint-of-delivery;

An Access Session Application User (component): by which user joins asession, find his/her point-of-delivery, and then the user can usehis/her resources;

Two Provider Agent (components): help Project developer/projectoperator/application user to establish trust relationships among them;send project-operator request to Developer-Operator Agent to establishnew session; or receive an invitation from User Agent for applicationuser. Each occurrence of access session will generate a Provider Agentinstance;

Two Initial Agent (components): are components independent of projectdeveloper, project operator, and application user. They are the initialaccess points in Resource Provision Domain. When project developer,project operator or application user try to contact or create sessionwith component in Resource Provision Domain, Initial Agent will reply amessage to Provider Agent. By interacting with Provider Agent, InitialAgent supports identity authentication and trust-relationshipestablishment between project developer/project operator/applicationuser and Resource Provision Domain;

A Developer-Operator Agent (component): is on behalf of projectdeveloper or project operator in Resource Provision Domain, acts as asingle contact point in access session, to control and manage newproject's Operator Service Session Manager. Contact information betweenproject developer/project operator and Resource Provision Domain can beobtained from Developer-Operator Agent as well;

A User Agent (component): is on behalf of application user in ResourceProvision Domain, acts as a single contact point in access session, tocontrol and manage new User Service Session Manager. Contact informationbetween application user and Resource Provision Domain can be obtainedfrom User Agent as well;

A Subscription Management Component: provides the management function ofsubscription-service information model in Resource Provision Domain.

In one embodiment of the present invention, an apparatus of mapping thelogical point-of-delivery to the physical point-of-delivery is provided,wherein the Service Session Layer includes following service sessionrelated components:

A Service Session Project Operator (component): is aproject-operator-related service component, acts as a concrete serviceendpoint. Through some proper interface, it allows project operator toaccess to Operator Service Session Manager, it also supports generalservice session control capabilities. For each service session involvingthis component, it will interact with Operator Service Session Manager;

A Service Session Application User (component): is anapplication-user-related service component, acts as a concrete serviceendpoint. Through some proper interface, it allows application user toaccess to User Service Session Manager, it also supports general servicesession control capabilities. For each service session involving thiscomponent, it will interact with User Service Session Manager;

A Service Factory (component): is a specific-service-related servicecomponent, used to create an object instance, upon the request fromDeveloper-Operator Agent or User Agent. If an application user requeststo create instance, it must have an interface being able to access toService Facility, and it shall send a proper request. A Service Factoryof multi-service-type provides individual interfaces for each type ofthe services separately. If necessary, Service Factory can continue tomanage the service components it generated;

A Service Session Manager (component): is used to control servicesession. It supports service capabilities shared by multiple applicationusers in the session. In service session, Service Session Managersupports to track and control virtual resource operations, it alsosupports the management capacities related to service session. ServiceSession Manager is instantiated by the Service Factory, which generatesa Service Session Manager upon request. When project developer leavesservices session or Service Session Manager is terminated by ServiceFactory, Service Session Manager instance will be deleted;

An Operator Service Session Manager (component): holds localproject-operator-related performance data and information. If anoperation only involves local project operator, Operator Service SessionManager will use its control and management capabilities; otherwise,Operator Service Session Manager and Service Session Manager will worktogether to support the operation. Operator Service Session Manager isinstantiated by Service Factory, which generates an Operator ServiceSession Manager upon request. When project operator leaves the session,Operator Service Session Manager instance will be deleted;

An Application User Session Manager (component): holds local applicationuser related performance data and information. If an operation onlyinvolves local application user, Application User Session Manager willuse its control and management capabilities; otherwise, Application UserSession Manager and Service Session Manager will work together tosupport the operation. Application User Session Manager is instantiatedby Service Factory, which generates an Application User Session Managerupon request. When application user leaves the session, Application UserSession Manager Instance will be deleted;

In the embodiment of the present invention, an apparatus of mapping thelogical point-of-delivery to the physical point-of-delivery is provided,wherein the Resource Session Layer includes one resource session relatedcomponent:

A Resource Session Manager (component): manages end-to-end resourceprovision, provides an interface which allows User Service SessionManager, Operator Service Session Manager, and Service Session Managerto create, modify, and delete end-to-end resource provision.

In one embodiment of the present invention, an apparatus of mapping thelogical point-of-delivery to the physical point-of-delivery is provided,wherein Provision Session Layer includes following provision sessionrelated components:

A Provision Coordinator (component): coordinates low level physicalresources;

A Provision Coordinator Factory (component): is used to createprovision-coordinator-object instance. A Provision Coordinator Factoryprovides individual interfaces for each type of resources separately. Ifnecessary, Provision Coordinator Factory can continue to manage theprovision coordinator objects it generated;

A Resource Provision Controller (component): is used to control andmanage a variety of low-level resources. Provision Coordinatorinstantiates a Resource Provision Controller upon eachresource-provision request. Resource Provision Controller contacts withResource, applies and uses physical resource to establish actual bindingof resource point.

Comparing to prior art, the present invention has following advantages:the technology solution of the present invention is to design a mappingsystem for mapping the logical point-of-delivery to the physicalpoint-of-delivery. With session mechanisms, it is capable of maintainingthe completeness and consistency of each project's point-of-deliveryenvironment after the mapping process. In fact, this is based on a newTINA-variation architecture which has four session layers: AccessSession Layer, Service Session Layer, Resource Session Layer, andProvision Session Layer. Resource Session Layer and Provision SessionLayer are among the novel features of the present invention. The servicetarget of the new architecture is enterprise data center, not thetelecommunication industry where TINA origins from anymore. The newarchitecture is left-right asymmetrical; it includes Project DeveloperDomain, Resource Provision Domain, and Application User Domain. Theresources it involves are extended from network-connection resource onlycovered by standard TINA, to all assets under management in anenterprise data center, including network, storage, and computingresources.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a structure diagram of a service delivery platformaccording to the present invention;

FIG. 2 illustrates a structure diagram of the new TINA-variationarchitecture according to the present invention;

FIG. 3 illustrates a structure diagram of the embodiment of a mappingsystem for mapping the logical point-of-delivery to the physicalpoint-of-delivery;

FIG. 4 illustrates a flowchart of project developer “a” sending arequest;

FIG. 5 illustrates a flowchart of application user “b” sending arequest;

FIG. 6 illustrates a flowchart of project operator “c” sending arequest; and

FIG. 7 illustrates a flowchart of Service Factory generating a servicesession.

DETAILED DESCRIPTION

The present invention and its embodiment will be further described infollowing sections with illustrations.

The embodiment of the present invention is a service delivery platform.The platform has four types of users: project developer, projectoperator, application user, and system operator.

Please see FIG. 1, which is the embodiment of the present invention, aservice delivery platform. The service delivery platform includes:Project Delivery Service Network 101, Project Logical EnvironmentService Network 102, Project Logical Environment Storage Network 103,Project Logical Environment Resource Network 104, Virtual ResourceNetwork 105, and Data Center Physical Resource Service Network Dividedby Project 106.

Project Delivery Service Network 101 includes: Project Core Service,Project Design Service, Project Delivery Scheduling, and ProjectSubscription Service;

In Project Logical Environment Service Network 102, the project deliveryand scheduling function supports automatic or manual “offline-online”environment switching, and supports the scheduling of point-of-deliveryfor multiple sets of projects. Project Logical Environment ServiceNetwork 102 includes the logical point-of-delivery of multiple sets ofoffline-projects and online-projects;

Project Logical Environment Storage Network 103: includes thepoint-of-delivery of multiple sets of offline-project instances;

Project Logical Environment Resource Network 104 includes: thepoint-of-delivery of multiple sets of online-project instances; forexample: project 3 and project 4 in FIG. 1 are in “online” status, i.e.making dedicated-resource deliveries for the subscriptions.

In Virtual Resource Network 105, virtual resources aggregate physicalresources of different configurations from different locations, toachieve resource consolidation regardless of types and deployments ofthe physical resources. Including unallocated and allocated virtualresources, Virtual Resource Network provides support (functions) ofexclusive holding or sharing virtual resources.

Data Center Physical Resource Service Network Divided by Project 106includes multiple sets of physical point-of-delivery. The Data CenterPhysical Resource Service Network Divided by Project 106 supportssubscription-delivery of the point-of-delivery, and supports sharingphysical resources by space or by time, including unallocated andallocated physical resources. For example: network, storage, computingresources. Besides various physical resources in physical data center,system operator is also responsible for defining the boundary ofphysical point-of-delivery.

By utilizing the latest technologies of computer and telecommunication,TINA defines a software architecture, which can organize complexbusiness and network-management-software structure more effectively. Andits service target is the telecommunication industry. The presentinvention has made some modifications and adjustments to TINA. The newarchitecture is used in a completely different field of resourcemanagement in enterprise data center. The embodiment of the presentinvention is based on the TINA-variation architecture. The newTINA-variation architecture and conventional TINA (and its applications)have following differences. Please see FIG. 2:

1) The service target of TINA architecture is the telecommunicationsindustry; the service target of TINA-variation architecture of thepresent invention is enterprise data center.

2) TINA architecture includes three session layers: Access SessionLayer, Service Session Layer, and Communication Session Layer; TheTINA-variation architecture of the present invention includes foursession layers: Access Session Layer 2004, Services Session Layer 2005,Resource Session Layer 2006, and Provision Session Layer 2007. Amongthem, Resource Session Layer 2006 and Provision Session Layer 2007 areamong the novel features of the present invention.

3) In TINA architecture, each session involves “consumer domain—retailerdomain—consumer domain”, that means, each layer of TINA architecture isleft-right symmetrical. This reflects the consumer-retailer-consumerrelationship of telecommunication services (for example, a phone call ormultimedia file transfer) between telecommunication industry andconsumers. The architecture of the present invention is left-rightasymmetrical. Please see FIG. 2, the left side is Project DeveloperDomain 2001, the middle part is Resource Provision Domain 2002, and theright side is Application User Domain 2003. The user of ProjectDeveloper Domain 2001 is project developer or project operator; the userof Application User Domain 2003 is application user. This reflects therelationship of different individuals managing or using a variety ofresources within an enterprise data center.

4) In TINA architecture, the bottom level resource only includes thenetwork connection resource provided to consumers. In the TINA-variationarchitecture of the present invention, the bottom level Resource 2050contains all resources managed by an enterprise data center, includingnetwork, storage, and computing resources.

Please see FIG. 2, which illustrates all the service componentsassociated with sessions within a service delivery platform of thepresent invention. These service components are distributed in ProjectDeveloper Domain 2001, Resource Provision Domain 2002, and ApplicationUser Domain 2003:

-   -   Project Developer Domain 2001 and Application User Domain 2003        contain all instantiated components at developer/operator/user        terminals.    -   Resource Provision Domain 2002 contains all instantiated        components and resources (i.e. Resource 2050) at one or several        resource provision points in the network.

Please see FIG. 2. In the TINA-variation architecture, all interactionsamong Project Developer Domain 2001, Resource Provision Domain 2002, andApplication User Domain 2003 are carried out in the sessions. TheTINA-variation architecture of the present invention includes fourlayers: Access Session Layer 2004, Service Session Layer 2005, ResourceSession Layer 2006, and Provision Session Layer 2007. We describe themin details as following:

A. Access Session Layer 2004

Access Session Layer 2004 includes all the components that play rolesduring an access session. Access session is used for identityauthentication of Project Developer 2100 and Application User 2300, andestablishing a terminal for service session.

Please see FIG. 2, wherein the components of access session include:Access Session Developer-Operator 2011, Access Session Application User2015, Provider Agent 2016 and 2019, Initial Agent 2012 and 2014,Subscription Management Component 2013, Developer-Operator Agent 2017,and User Agent 2018.

Please see FIG. 2, where Access Session Developer-Operator 2011 andAccess Session Application User 2015 both have a graphical userinterface for identity authentication of Project Developer 2100, ProjectOperator 2200, or Application User 2300. Provider Agent 2016 is used byAccess Session Developer-Operator 2011 for communicating with ResourceProvision Domain 2002. The communication process carried out throughInitial Agent 2012. Initial Agent 2012 obtains subscription informationof Project Developer 2100 from Subscription Management Component 2013,and authenticates the identity of Project Developer 2100 according tothe subscription information, and then starts Developer-Operator Agent2017. Provider Agent 2016 and Developer-Operator Agent 2017 worktogether to establish a secure personal access session. Thus, ProjectDeveloper 2100 can prepare a service session and subscribe the resourcesin the point-of-delivery. Access process of Project Operator 2200 isalmost identical to the access process of Project Developer 2100described above, so the repetitious details need not be given here.

Please see FIG. 2, Provider Agent 2019 is used by Access SessionApplication User 2015 for communicating with Resource Provision Domain2002. The communication process carried out through Initial Agent 2014.Initial Agent 2014 obtains subscription information of Application User2300 from Subscription Management Component 2013, and authenticates theidentity of Application User 2300 according to the subscriptioninformation, and then starts User Agent 2018. Provider Agent 2019 andUser Agent 2018 work together to establish a secure personal accesssession. Thus, Application User 2300 can choose to join a particularservice session.

Before a Project Developer 2100 starts an access session, he or she mustinstall project development tool on the local machine as terminal.Project Developer 2100 can logs in and start the subscription service asan anonymous user. Subscription service allows Project Developer 2100 tofill in personal account data, such as login user name and password(hereafter Project Developer 2100 is no longer an anonymous user).Subscription service also allows Project Developer 2100 to subscribe aset of resources provided in Resource Provision Domain 2002—ProjectDeveloper 2100 can plan a logical point-of-delivery. The logicalpoint-of-delivery includes server, storage, and network resources.

Before Application User 2300 opens an access session, he or she mustinstall the project execution tool on the local machine as terminal.After Application User 2300 creates an account, he or she can request tojoin a particular service session.

Before Project Operator 2200 (can be regarded as a super-user) opens anaccess session, Project Operator 2200 must install the projectmanagement tool on the local machine as terminal. After Project Operator2200 login, he or she can see the session list of un-launched andoff-line sessions. Project Operator 2200 can choose when and whichsession to have “offline—online” or “online—offline” switching. He orshe can also approve Application User 2300 to join a particular servicesession.

In addition, Application User 2300 can also be invited by ProjectOperator 2200 to join the service session. Application User 2300 mayaccept or decline the invitation. If the invitation is accepted,Application User 2300's Service Session Application User 2026 will bestarted, and the user will be added into the component. Therefore,during a session, there may be new invitations arriving to ApplicationUser 2300, i.e., Provider Agent 2019 leads to open a dialog window forApplication User 2300, let the user to choose whether he/she shallaccept or decline the invitation.

Subscription Management Component 2013 interacts with other componentsmainly during access session. In the authentication processes of ProjectDeveloper 2100, Project Operator 2200, and Application User 2300,Initial Agent 2012 and 2014 extract the subscription information ofProject Developer 2100, Project Operator 2200, and Application User 2300by contacting with Subscription Management Component 2013.Developer-Operator Agent 2017 and User Agent 2018 also extract theinformation of Project developer 2100, Project Operator 2200, andApplication User 2300, and obtain or store the attributes of them bycontacting with Subscription Management Component 2013. SinceSubscription Management Component 2013 also contains the description ofservices, in service session, Service Factory 2023 also extracts neededinformation to instantiate concrete components by contactingSubscription Management Component 2013.

Subscription Management Component 2013 can manage the whole package ofservices offered by Resource Provision Domain 2002, including thecontract between Application User 2300 and service. Therefore,Subscription Management Component 2013 may contain multiple logicalpoint-of-delivery and the parameters of various resources in the logicalpoint-of-delivery. This component provides the functions mainly are:

-   -   Create, modify, delete, and query subscriber (e.g. related        application user, application use group, etc.);    -   Create, modify, delete, and query subscriber related        information;    -   Create, modify, delete, and query service contract        (description-file definition of the subscription service);    -   Extract the list of services, including the service description        file extracted from Service Management Component 2013 for the        application user (or terminal).

When an access session is successfully completed, Service Factory 2023can initiate a service session to (automatically) select one or morevirtual resources needed. Application User 2300 can find a variety ofvirtual resources defined by logical point-of-delivery in servicesession. In general case, each development project is corresponding to alogical point-of-delivery; each logical point-of-delivery needs aservice session.

B. Service Session Layer 2005

Service Session Layer 2005 of the TINA-variation architecture can holdone or multiple service sessions, and carry out (virtual) resourcebindings in Resource Provision Domain 2002. Usually a service session iscorresponding to one project.

Please see FIG. 2. FIG. 2 includes all the components in Service SessionLayer 2005. In Resource Provision Domain 2002, when Service Factory 2023receives a request from Developer-Operator Agent 2017, it will createService Session Manager 2024 and Operator Service Session Manager 2022.After Service Factory 2023 receives a request from User Agent 2018, itwill create User Service Session Manager 2025.

The present invention only supports single Service Facility 2023;Service Factory 2023 creates a Service Session Manager 2024 object foreach service session through the platform. Service Factory 2023 canobtain component names of Service Session Manager 2024, Operator ServiceSession Manager 2022, and User Service Session Manager 2025corresponding to a concrete service session from Subscription ManagementComponent 2013. The reason of using single Service Factory 2023 isbecause there is no need of using multiple Service Factory 2023 in ourimplementation. Once single Service Factory 2023 has difficulty to copewith the situation while the number of service increases, we can easilycreate additional Service Facility 2023 (i.e., supports multiple ServiceFacility 2023).

In Service Session Layer 2005, Service Session Project Operator 2021 andService Session Application User 2026 are created by Provider Agent 2016and 2019, respectively. Services Session Project Operator 2021 providesservices to Project Operator 2200, and Service Session Application User2026 provides services to Application User 2300.

Service Session Manager 2024 maintains a global view of a session,including the session participators, the resource bindings, and theresource model. In another word, the session model is not distributed inplaces where Service Session Manager 2024, each Operator Service SessionManager 2022, and User Service Session Manager 2025 locate. This designmethod reflects the deep consideration that a session model must beconsistent and must be easy to maintain. Service Session Manager 2024 isthe control point of accessing the session model information.

A session consists of various elements: session participators, resourcebindings, and relationships that control the session. Therefore, asession model is fixed—so there is no negotiation operation regardingwhich model to support when a service is starting. Operator ServiceSession Manager 2022 and User Service Session Manager 2025 only act asthe security controllers of accessing Services Session Manager 2024, aswell as the service windows of Services Session Project Operator 2021and Service Session Application User 2026.

Session participators (i.e. each application user) must have a clearinvitation to join a service session. In services session, adding ordeleting a resource is carried out through the interface of ServiceSession Manager 2024.

Concrete services are built upon the components in Service Session Layer2005. These components include Service Session Project Operator 2021,Service Session Application User 2026, Service Session Manager 2024,Operator Service Session Manager 2022, and User Service Session Manager2025. These components provide the service session management functionswhich are necessary for each service. Through these service sessionmanagement functions, service session can be started or deleted.Services session can also add, modify, or delete session participantsand bound resources.

C. Resource Session Layer 2006

Components in Resource Session Layer 2006 are used to manage resourcenetwork and control resource session. Resource session provides aresource binding view of different session participants. Usually, aresource session uses QoS (Quality of Service) parameters and abstractlogical-resource description to define a resource binding. Resourcesession encapsulates some details, which involve the matching processbetween QoS request and concrete resource features (such as server,storage, and network capabilities).

Please see FIG. 2, there is only one component playing role in resourcesession: Resource Session Manager 2032 manages end-to-end resourceprovision. The capabilities of each resource point should match with therequirement, and the state of concrete resource should be “available”.The results of checking QoS parameters and resource capabilities willbecome various conditions of mapping virtual resources into physicalresources. Every allocated virtual resource belongs to some onlinelogical point-of-delivery.

Each resource point has some specific resource capabilities. Forexample, CPU performance, storage size. These requirements are providedas input to Resource Session Manager 2032, in order to select a resourceprovider. The resource provider should have a contract-description filethat used to control the concrete physical resource.

D. Provision Session Layer 2007

Components in Provision Session Layer 2007 are used to manage andcontrol provision session. Provision session hides network-provisiondetails from resource session. Under the premise of existing specialresources of network-provision details mapping to several provisionnetworks, a provision session may across multiple provision networks, asituation both service session and provision session will know.

Please see FIG. 2. Provision Session Layer 2007 includes threecomponents: Provision Coordinator Factory 2041, Provision Coordinator2042, and Resource Provision Controller 2043. Provision CoordinatorFactory 2041 is a factory of Provision Coordinator 2042. ProvisionCoordinator 2042 creates and controls whole provision session.

A provision session consists of two parts: network-resource points andnetwork provisions. Each network provision is created and controlled byindividual Resource Provision Controller 2043. Provision Coordinator2042 instantiates a Resource Provision Controller 2043 for each networkprovision request. Resource Provision Controller 2043 contacts with avariety of resources in Resource 2050, applies and uses physicalresources in order to establish actual bindings of resource points inthe network. Each allocated virtual resource can be mapped to one ormultiple resource points, i.e. delivered by one or multiple physicalresources.

In the TINA-variation architecture, the session protocols are capable ofmaintaining the completeness and consistency of a project plan/design'spoint-of-delivery environment.

FIG. 3 depicts two concrete examples of how the service deliveryplatform of the present invention maintains the completeness andconsistency of project's point-of-delivery environment in the processesof mapping logical point-of-delivery into physical point-of-delivery.

Please see FIG. 3, where a project developer has designed twopoint-of-delivery environments: Project A's Logical Point-of-Delivery 31and Project B's Logical Point-of-Delivery 32. Server 311 and server 321are two identical servers, which have been allocated to Project A'sLogical Point-of-Delivery 31 and Project B's Logical Point-of-Delivery32, respectively.

When the two sets of logical point-of-delivery are both on-line, theyeither exclusively hold or share each virtual resource in AllocatedVirtual Resource 33: Server 311 holds Virtual Server 341; Server 321holds Virtual Server 351. (In FIG. 3, Network 312 holds Virtual Network342; Network 322 holds Virtual Network 352; shared Storage 313 andStorage 323 holds Virtual Storage 345.)

Please see FIG. 3. Virtual Server 341 is delivered by virtual machine VM361 in Physical Point-of-Delivery 36; Virtual Server 351 is delivered byvirtual machine VM 362 in Physical Point-of-Delivery 36. Virtual machineVM 361 and VM 362 share Physical Server 1 in Physical Point-of-Delivery36 through time sharing. When virtual machine VM 361 switches to virtualmachine VM 362, Virtual Server 341 is therefore suspended and VirtualServer 351 starts to execute. At this moment, the virtual networkcollaborating with Virtual Server 351 must be Virtual Network 352 ratherthan Virtual Network 342, while virtual storage (Virtual Storage 345)may remain unchanged. This is because Virtual Server 351, VirtualNetwork 352, and Virtual Storage 345 are belong to the samepoint-of-delivery (i.e., Project B's Point-of-Delivery 35), but VirtualNetwork 342 is not. Session protocol can record resources in the samepoint-of-delivery into same session, thus it can maintain thecompleteness of the project plan/design's point-of-delivery environment.

Please see FIG. 3. When virtual machine VM 371 in PhysicalPoint-of-Delivery 37 is idle, or when virtual machine VM 362 in PhysicalPoint-of-Delivery 36 fails, the delivery of Virtual Server 351 can bescheduled from virtual machine VM 362 to virtual machine VM 371. Becausethe session protocol is “stateful”, in point-to-point resource provisionprocess it can handle failure and make recovery. It can also takeadvantage of proxy/gateway to search and maintain resource states acrossvirtual network cluster.

The session protocol ensures the state of workload on Virtual Server 351is consistent with the original one after the workload migrates fromvirtual machine VM 362 to virtual machine VM 371, i.e. session protocolcan maintain the completeness of the project plan/design'spoint-of-delivery environment.

One of the common session protocols is SIP (session initiationprotocol). The session package header of SIP contains user identity andhistory record of proxy transmission. Session instruction of SIP cansynchronize checkpoints. A user request will generate access sessionfirst, and the main workload of the session is user's access request andfinal response. Access request will generate service session after therequest has been authenticated. In the service session, the mainworkload is logical point-of-delivery. Logical point-of-delivery anduser requested resource are bound together. When a project is completed,they will be unbound. And the service session will be over. The mainworkloads of resources session are the logical resources to be competed,selected, and isolated. The main workloads in provision session areto-be-converged physical resourced in Resource 2050.

In our experience, the proposed architecture of the present invention isquite practical. It is a very flexible model that can be dynamicallyimplemented through PCDM (Project Component Decomposition Method). Oncebeing instantiated, you can easily integrate the components into theembodiment of the present invention, such as the service deliveryplatform in the present invention.

Traditionally, TINA describes telecommunication services through aseries of interactive computing objects called “components”. The majorcomponents in TINA architecture can be classified into two types ofcomponents: General Service Component and Specific Service Component.General Service Component serves for public use; Specific ServiceComponent serves for specific service use (such as representing servicelogic, data, management, etc.).

Although the internal mechanisms of the components in present inventionare very different from original TINA's, the description of embodimentstill uses the term of “component”. With illustrating figures, thedetailed method of the present invention is introduced through theembodiment as following.

Please see FIG. 2, where access session related components are: AccessSession Developer-Operator 2011, Access Session Application User 2015,Provider Agent 2016, 2019, Initial Agent 2012, 2014, Developer-OperatorAgent 2017, User Agent 2018, and Subscription Management Component 2013.

Access Session Developer-Operator 2011 is used to create a new session.In the session, project developer can plan a logical point-of-delivery,in order to establish project-specific resource requirements. Projectoperator can set up a schedule to activate a project at a specific timewhen the logical point-of-delivery will be mapped to physicalpoint-of-delivery.

In Access Session Application User 2015, a user can join a session andfind his/her point-of-delivery. Then the user can use his/her resources.

Provider Agent 2016 and 2019 are used to help project developer/projectoperator/application user to establish trust relationships between themand provider (i.e., Resource Provision Domain 2002). They sendproject-operator request to Developer Operator Agent 2017 to create anew session, or receive application-user invitation from User Agent2018. Each creation of an access session will generate an instance ofProvider Agent 2016 or 2019.

Initial Agent 2012 and 2014 are the components independent of projectdeveloper, project operator and application user. In Resource ProvisionDomain 2002, they are initial access points. When a project developer,project operator or application user wants to establish a contact orcreate a session with Resource Provision Domain 2002, Initial Agent 2012or 2014 will reply a message to Provider Agent 2016 or 2019. Byinteracting with Provider Agent 2016 or 2019, Initial Agent 2012 or 2014supports project developer, project operator or application user toauthenticate his/her identity and establish trust relationship withResource Provision Domain 2002.

Developer-Operator Agent 2017 represents project developer or projectoperator in Resource Provision Domain 2002. In access session, it actsas a single contact point to control and manage new Operator ServiceSession Manager 2022. The contact information between projectdeveloper/project operator and Resource Provision Domain 2002 can alsobe obtained from Developer-Operator Agent 2017.

User Agent 2018 represents application user in Resource Provision Domain2002. In access session, it acts as a single contact point to controland manage new User Service Session Manager 2025. The contactinformation between application user and Resources Provision Domain 2002can also be obtained from User Agent 2018.

Subscription Management Component 2013 provides functions of managingsubscription-service-information model in Resource Provision Domain2002.

Please see FIG. 2, where service session related components include:Services Session Project Operator 2021, Service Session Application User2026, Service Factory 2023, Service Session Manager 2024, OperatorService Session Manager 2022, and User Service Session Manager 2025.

Services Session Project Operator 2021 is a project operator relatedservice component. It acts as a concrete service endpoint. Throughproper interface, it enables project operator to access Operator ServiceSession Manager 2022. It also supports some general service sessioncontrol capabilities. For each service session it involves, it willinteract with Operator Service Session Manager 2022.

Services Session Application User 2026 is an application user relatedservice component. It acts as a concrete service endpoint. Throughproper interface, it enables application user to access User ServiceSession Manager 2025. It also supports some general service sessioncontrol capabilities. For each service session it involves, it willinteract with User Service Session Manager 2025.

Service Factory 2023 is a concrete-service-related service component,which is used to create object instances (including instances ofOperator Service Session Manager 2022, User Service Session Manager2025, and Service Session Manager 2024). The creation is usuallyrequested by Developer-Operator Agent 2017 or User Agent 2018. Ifapplication user object requests the creation, it must have an interfacefor accessing Service Factory 2023, and send a proper request. Amulti-service type Service Factory 2023 should provide differentinterfaces for each type of services, respectively. If necessary,Service Factory 2023 can continue to manage the service component itgenerated.

Service Session Manager 2024 is used for service session control. Inservice session, Service Session Manager 2024 supports servicecapabilities which can be shared by multiple applications users. Inservice session, Service Session Manager 2024 supports operations oftracking and controlling (virtual) resources. It also supportsmanagement capabilities related to service session. Service SessionManager 2024 is instantiated by Service Factory 2023. Service Factory2023 generates a Service Session Manager 2024 upon the request. And theinstance of Service Session Manager 2024 will be deleted when theproject developer leaves the service session or Service Session Manager2024 is terminated by Service Factory 2023.

Operator Service Session Manager 2022 holds local project operatorrelated performance data and information. If an operation only involveslocal project operator, Operator Service Session Manager 2022 will useits own control and management capabilities; otherwise, Operator ServiceSession Manager 2022 and Service Session Manager 2024 will support theoperation together. Operator Service Session Manager 2022 is alsogenerated by the instantiation of Service Factory 2023. Service Factory2023 generates an Operator Service Session Manager 2022 upon therequest. The instance of Operator Service Session Manager 2022 will bedeleted when the project developer leaves the session.

User Service Session Manager 2025 holds local application-user relatedperformance data and information. If an operation only involves localapplication user, User Service Session Manager 2025 will use its owncontrol and management capabilities; otherwise, User Service SessionManager 2025 and Service Session Manager 2024 will support the operationtogether. User Service Session Manager 2025 is also generated by theinstantiation of Service Factory 2023; Service Factory 2023 generates aUser Service Session Manager 2025 upon the request, the instance of UserService Session Manager 2025 will be deleted when application userleaves the service session.

Please see FIG. 2, resource session related component includes ResourceSession Manager 2032 only. Resource Session Manager 2032 is used tomanage end-to-end resource provision. It provides an interface thatallows User Service Session Manager 2025, Operator Services SessionManager 2022, and Service Session Manager 2024 to create, modify, anddelete end-to-end resource provision.

Provision session related components include: Provision Coordinator2042, Provision Coordinator Factory 2041, and Resource ProvisionController 2043.

Provision Coordinator 2042 is used to coordinate low-level physicalresources.

Provision Coordinator Factory 2041 is used to create provisioncoordinator object instance. Provision Coordinator Factory 2041 providesindividual interface for each type of resources. If necessary, ProvisionCoordinator Factory 2041 can continue to manage the provisioncoordinator object it generated.

Resource Provision Controller 2043 is used to control and manage avariety of low-level resources. Provision Coordinator 2042 instantiatesa Resource Provision Controller 2043 for each resource-provisionrequest. Resource Provision Controller 2043 contacts with Resource 2050,applies and uses physical resource to establish the actual binding ofresource point in the network.

The session unrelated component is Resource 2050. Resource 2050 refersto a variety of physical resources, including IT, storage, and networkresources.

Based on FIG. 1 and FIG. 2, the flow processes of an embodiment of thepresent invention are described as following.

Please see FIG. 4. Project Developer“a” makes a request. The flowprocess following the request includes:

Project Developer“a” actives Access Session Developer-Operator 2011, andsends an access request; Access Session Developer-Operator 2011 sendsprompt to“a” to input network authentication information.

Access Session Developer-Operator 2011 sends“a”'s request andauthentication information to Provider Agent 2016; then Provider Agent2016 forwards them to Initial Agent 2012.

Initial Agent 2012 obtains user-related data from SubscriptionManagement Component 2013 and makes identity authentication for ProjectDeveloper“a”. (if necessary, Initial Agent 2012 will interact directlywith user through Provider Agent 2016). If the authentication fails,Initial Agent 2012 will reject Project Developer“a” through ProviderAgent 2016 and Access Session Developer-Operator 2011; if theauthentication is successful, Initial Agent 2012 will notifyDeveloper-Operator Agent 2017; Developer-Operator Agent 2017 sendsproject attribute data and terminal attribute data to Provider Agent2016 and continues the follow-up process.

Supported by Project Delivery Service Network 101, Project Developer“a”can make project designs, for example: planning the logicalpoint-of-delivery required by Project 3, i.e. network, storage, andcomputing resource environment. Some projects also include applications.A completed project design (corresponding to a logicalpoint-of-delivery) will be in offline status.

Developer-Operator Agent 2017 sends a request of generating servicemanager to Service Factory 2023 based on the attributes of ProjectDeveloper“a”'s point-of-delivery.

Please see FIG. 5. Application User“b” makes a request. The flow processfollowing the request includes:

Application User“b” activates Access Session Application User 2015 andsends an access request; Access Session Application User 2015 sendsprompt to“b” to input network authentication information.

Access Session Application User 2015 sends“b”'s request andauthentication information to Provider Agent 2019; then Provider Agent2019 forwards them to Initial Agent 2014.

Initial Agent 2014 obtains user-related data from SubscriptionManagement Component 2013 and makes identity authentication forApplication User“b”. (if necessary, Initial Agent 2014 will interactdirectly with user through Provider Agent 2019). If the authenticationfails, Initial Agent 2014 will reject Application User“b” throughProvider Agent 2019 and Access Session Application User 2015; if theauthentication is successful, Initial Agent 2014 will notify User Agent2018; User Agent 2018 sends project attribute data and terminalattribute data to Provider Agent 2019 and continues the follow-upprocess.

Supported by Project Delivery Service Network 101, Application User“b”can subscribe a project.

User Agent 2018 sends a request of generating service manager to ServiceFactory 2023 based on the attributes of User“b”.

Please see FIG. 6. Project Operator“c” makes a request. The flow processfollowing the request includes:

Project Operator“c” actives Access Session Developer-Operator 2011 andsends an access request; Access Session Developer-Operator 2011 sendsprompt to“c” to input network authentication information.

Access Session Developer-Operator 2011 sends“c”'s request andauthentication information to Provider Agent 2016; then Provider Agent2016 forwards them to Initial Agent 2012.

Initial Agent 2012 obtains user-related data from SubscriptionManagement Component 2013 and makes identity authentication for ProjectOperator“c”. (if necessary, Initial Agent 2012 will interact directlywith user through Provider Agent 2016). If the authentication fails,Initial Agent 2012 will reject Project Operator“c” through ProviderAgent 2016 and Access Session Developer-Operator 2011; if theauthentication is successful, Initial Agent 2012 will notifyDeveloper-Operator Agent 2017; Developer-Operator Agent 2017 sendsproject attribute data and terminal attribute data to Provider Agent2016 and continues the follow-up process.

Supported by Project Logical Environment Service Network 102, ProjectOperator“c” can make project scheduling, for example: set the time whenswitching Project 3 from offline status to online status (i.e., the timewhen mapping the logical point-of-delivery to physicalpoint-of-delivery).

Please see FIG. 7. Service Factory 2023 generates a service session, andthe flow process following the service-session creation includes:

If Project Operator“c” and Application User“b” are both in the sessionof Project 3, Service Factory 2023 will generate Operator ServiceSession Manager 2022, User Service Session Manager 2025, and ServiceSession Manager 2024 for Project 3. If only Project Operator“c” existsin the session of Project 3, Service Factory 2023 will generate OperatorService Session Manager 2022 and Service Session Manager 2024.

Service Session Project Operator 2021 connects to Operator ServiceSession Manager 2022 and Service Session Manager 2024 according to therequests of Provider Agent 2016 and Developer-Operator Agent 2017,respectively. Thus, Project Operator“c” has completed the access sessionand enters service session.

If Application User“b” is in the session of Project 3, Service SessionApplication User 2026 connects to User Service Session Manager 2025 andService Session Manager 2024 according to the requests of Provider Agent2019 and User Agent 2018, respectively. Thus, Application User“b” hascompleted the access session and entered service session.

In services session, Service Session Manager 2024 sends (virtual)resource request to Resource Session Manager 2032 in Resource SessionLayer 2006. Resource Session Manager 2032 controls low-level (physical)resources in Resource 2050 through Provision Coordinator Factory 2041,Provision Coordinator 2042 and Resource Provision Controller 2043 inProvision Session Layer 2007.

Supported by Virtual Resource Network 105 (mostly supported by virtualresource exclusive holding or sharing), Resource Session Manager 2032manages end-to-end resource provision. Each allocated virtual resourcehas a corresponding resource session. Resource Session Manager 2032 alsoprovides an interface for Services Session Layer 2005, which allows UserService Session Manager 2025/Operator Service Session Manager2022/Service Session Manager 2024 to create, modify, or deleteend-to-end (virtual) resource provision. For example, Class I server isneeded in Project 3, then Service Session Manager 2024 will establish acorresponding resource session for Class I server.

Supported by Data Center Physical Resource Service Network Divided byProject 106, Provision Coordinator 2042 coordinates a variety oflow-level (physical) resources. At the time of subscription delivery,Provision Coordinator Factory 2041 creates an object instance ofProvision Coordinator 2042 (a Provision Coordinator Factory 2041 shouldprovide individual interface for each type of resources). For example:Provision Coordinator Factory 2041 creates a Provision Coordinator 2042for Class I server.

Supported by Data Center Physical Resource Service Network Divided byProject 106, Resource Provision Controller 2043 controls and manages avariety of low-level resources. Provision Coordinator 2042 instantiatesa Resource Provision Controller 2043 for each resource-provision request(for example: a Class I server request). Resource Provision Controller2043 contacts with resources (e.g., a Class I physical server), so thatApplication User“b” can apply and use physical resources in the network.

If Application User“b” is in Project 3's session, Application User“b”can use resources in the physical point-of-delivery including Class Iphysical server through Service Session Application User 2026. It isnoteworthy that the process of mapping logical point-of-delivery tophysical point-of-delivery is transparent to user.

The above embodiment is provided to those skilled in the art toimplement and utilize the present invention. Those who skilled in theart may make various modification or variation to the embodimentdescribed above without departing from the innovative idea of thepresent invention. Therefore the scope of the present invention shallnot limit to the above embodiment, and it should be in the maximum rangeof innovative features that are consistent with the claims mentioned.

What is claimed is:
 1. A computer implemented system including at leastone computer processor for executing a mapping system of mapping logicalpoint-of-delivery to physical point-of-delivery for cloud computingresource management in enterprise data center, wherein the mappingsystem is executed in a service delivery platform according to a newTelecommunication Information Networking Architecture (TINA)-variationarchitecture; a service target of the TINA-variation architecture is anenterprise data center; the TINA-variation architecture includes anAccess Session Layer, a Service Session Layer, a Resource Session Layer,and a Provision Session Layer, the TINA-variation architecture isleft-right asymmetrical; physical resources of the TINA-variationarchitecture include IT resources, storage resources, and networkresources; the service delivery platform is used by a project developer,a project operator, an application user, and a system operator; whereinthe service delivery platform includes a Project Delivery ServiceNetwork, a Project Logical Environment Service Network, a ProjectLogical Environment Storage Network, a Project Logical EnvironmentResource Network, a Virtual Resource Network, and a Data Center PhysicalResource Service Network Divided by Project; the Project DeliveryService Network includes a Project Core Service, a Project DesignService, a Project Delivery Scheduling, and a Project SubscriptionService; the Project Logical Environment Service Network includesmultiple sets of offline-projects' and online-projects' logicalpoint-of-delivery, in which the project-delivery-and-scheduling functionsupports automatic or manual offline-online environment switching, andsupports scheduling multiple sets of projects' point-of-delivery; theProject Logical Environment Storage Network includes multiple sets ofoffline-project instances' point-of-delivery; the Project LogicalEnvironment Resource Network includes multiple sets of online-projectinstances' point-of-delivery; the Virtual Resource Network in whichvirtual resources aggregate physical resources of differentconfigurations and different locations, is configured to achieveresource consolidation regardless of type and deployment of the physicalresources; wherein the virtual resource network includes unallocated andallocated virtual resources and the Virtual Resource Network providessupport of exclusive holding or sharing virtual resources; the DataCenter Physical Resource Service Network Divided by Project includesmultiple sets of physical point-of-delivery; the Data Center PhysicalResource Service Network Divided by Project supports subscription andcommitment of the point-of-delivery, and supports sharing physicalresources by space or by time; and the Data Center Physical ResourceService Network Divided by Project includes unallocated and allocatedphysical resources; wherein the Access Session Layer includes accesssession related components: an Access Session Developer-Operator, anAccess Session Application User, two Provider Agents, two InitialAgents, a Developer-Operator Agent, a User Agent, and a SubscriptionManagement Component; wherein the Access Session Developer-Operator isused to create a new session in which the project developer plans alogical point-of-delivery, while the developer obtains theproject-specific resource requirements; the project operator schedulesthe activate time, the moment when the project's logicalpoint-of-delivery maps to physical point-of-delivery; the Access SessionApplication User by which user joins a session, finds thepoint-of-delivery, and then the user can use the resources; the TwoProvider Agent help project developer, project operator or applicationuser to establish trust relationships among them; send aproject-developer request to the Developer-Operator Agent to establishnew session; or receive an invitation from the User Agent forapplication user; wherein each access session creation will generate aProvider Agent instance; the Two Initial Agent are independent ofproject developer, project operator, and application user; the twoinitial agent are the initial access points in a Resource ProvisionDomain; When project developer, project operator or application user tryto contact or create session with Resource Provision Domain, InitialAgent will reply a message to Provider Agent; By interacting withProvider Agent, Initial Agent supports identity authentication and trustrelationship establishment between project developer/projectoperator/application user and Resource Provision Domain; theDeveloper-Operator Agent is on behalf of project developer or projectoperator in the Resource Provision Domain, and acts as a single contactpoint in access session, to control and manage new project's OperatorService Session Manager, contact information between the projectdeveloper or project operator and the Resource Provision Domain can beobtained from the Developer-Operator Agent as well; the User Agent is onbehalf of application user in the Resource Provision Domain, and acts asa single contact point in access session to control and manage a newUser Service Session Manager; contact information between theapplication user and the Resource Provision Domain can be obtained fromthe User Agent as well; the Subscription Management Component providesthe management function of subscription-service information model in theResource Provision Domain.
 2. The system of claim 1, wherein theTINA-variation architecture includes several session-related servicecomponents in the service delivery platform; the service components aredistributed in a Project Development Domain, a Resource ProvisionDomain, and an Application User Domain; the Project Development Domainand Application User Domain contain all instantiated components atdeveloper, operator or user terminal; the Resource Provision Domaincontains all instantiated components and resources at one or severalresource provision points in the network.
 3. The system of claim 1,wherein the Provision Session Layer includes provision session relatedcomponents: a Provision Coordinator, a Provision Coordinator Factory,and a Resource Provision Controller, wherein the provision coordinatorcoordinates low level physical resources; the Provision CoordinatorFactory is configured to create provision coordinator object instance;and the Provision Coordinator Factory provides individual interface foreach type of resources separately; if necessary, the ProvisionCoordinator Factory can continue to manage the provision coordinatorobjects it generated; the Resource Provision Controller is used tocontrol and manage a variety of low-level resources; the ProvisionCoordinator instantiates individual Resource Provision Controller uponeach resource-provision request; the Resource Provision Controllercontacts with Resource, applies and uses physical resource to establishactual binding of resource point.
 4. A computer implemented systemincluding at least one computer processor for executing a mapping systemof mapping logical point-of-delivery to physical point-of-delivery forcloud computing resource management in enterprise data center, whereinthe mapping system is executed in a service delivery platform accordingto a new Telecommunication Information Networking Architecture(TINA)-variation architecture; a service target of the TINA-variationarchitecture is an enterprise data center; the TINA-variationarchitecture includes an Access Session Layer, a Service Session Layer,a Resource Session Layer, and a Provision Session Layer; theTINA-variation architecture is left-right asymmetrical; physicalresources of the TINA-variation architecture include IT resources,storage resources, and network resources; the service delivery platformis used by a project developer, a project operator, an application user,and a system operator; wherein the service delivery platform includes aProject Delivery Service Network, a Project Logical Environment ServiceNetwork, a Project Logical Environment Storage Network, a ProjectLogical Environment Resource Network, a Virtual Resource Network, and aData Center Physical Resource Service Network Divided by Project; theProject Delivery Service Network includes a Project Core Service, aProject Design Service, a Project Delivery Scheduling, and a ProjectSubscription Service; the Project Logical Environment Service Networkincludes multiple sets of offline-projects' and online-projects' logicalpoint-of-delivery, in which the project-delivery-and-scheduling functionsupports automatic or manual offline-online environment switching, andsupports scheduling multiple sets of projects' point-of-delivery; theProject Logical Environment Storage Network includes multiple sets ofoffline-project instances' point-of-delivery; the Project LogicalEnvironment Resource Network includes multiple sets of online-projectinstances' point-of-delivery; the Virtual Resource Network in whichvirtual resources aggregate physical resources of differentconfigurations and different locations, is configured to achieveresource consolidation regardless of type and deployment of the physicalresources; wherein the virtual resource network includes unallocated andallocated virtual resources and the Virtual Resource Network providessupport of exclusive holding or sharing virtual resources; the DataCenter Physical Resource Service Network Divided by Project includesmultiple sets of physical point-of-delivery; the Data Center PhysicalResource Service Network Divided by Project supports subscription andcommitment of the point-of-delivery, and supports sharing physicalresources by space or by time; and the Data Center Physical ResourceService Network Divided by Project includes unallocated and allocatedphysical resources; wherein the Service Session Layer includes servicesession related components: a Service Session Project Operator, aServices Session Application User, a Service Factory, a Service SessionManager, an Operator Service Session Manager, and an Application UserSession Manager; wherein the Service Session Project Operator is aproject-operator-related service component, and acts as a concreteservice endpoint; through some proper interface, the Service SessionProject Operator allows a project operator to access to the OperatorService Session Manager; the Service Session Project Operator alsosupports general service session control capabilities; for each servicesession involving this component, it will interact with the OperatorService Session Manager; the Services Session Application User is anapplication-user-related service component, and acts as a concreteservice endpoint; through some proper interface, the Services SessionApplication User allows an application user to access to the UserService Session Manager; the Services Session Application User alsosupports general service session control capabilities; for each servicesession involving this component, it will interact with the User ServiceSession Manager; the Service Factory is a specific-service-relatedservice component, and is used to create an object instance upon therequest from Developer-Operator Agent or User Agent; if an applicationuser requests to create an instance, it must have an interface beingable to access to the service facility, and it shall send a properrequest, the Service Factory of multi-service type provides individualinterfaces for each type of the services separately; if necessary, theService Factory can continue to manage the service component itgenerated; the Service Session Manager is used in service sessioncontrol; the Service Session Manager supports service capabilitiesshared by multiple application users in the session; in a servicesession, the Service Session Manager supports to track and controlvirtual resource operations, the Service Session Manager also supportsthe management capacities related to service session; the ServiceSession Manager is instantiated by the Service Factory, which generatesa Service Session Manager upon request; when a project developer leavesservices session or the Service Session Manager is terminated by theService Factory, the Service Session Manager Instance will be deleted;the Operator Service Session Manager holds localproject-operator-related performance data and information; if anoperation only involves local project operator, the Operator ServiceSession Manager will use its control and management capabilities;otherwise, the Operator Service Session Manager and the Service SessionManager will work together to support the operation; the OperatorService Session Manager is instantiated by the Service Factory, whichgenerates an Operator Service Session Manager upon request; when aproject developer leaves the session, the Operator Service SessionManager Instance will be deleted; the Application User Session Managerholds local application user related performance data and information;if an operation only involves local application user, the ApplicationUser Session Manager will use its control and management capabilities;otherwise, the Application User Session Manager and the Service SessionManager will work together to support the operation; the ApplicationUser Session Manager is instantiated by the Service Factory, whichgenerates an Application User Session Manager upon request; when anapplication user leaves the session, the Application User SessionManager Instance will be deleted.
 5. A computer implemented systemincluding at least one computer processor for executing a mapping systemof mapping logical point-of-delivery to physical point-of-delivery forcloud computing resource management in enterprise data center, whereinthe mapping system is executed in a service delivery platform accordingto a new Telecommunication Information Networking Architecture(TINA)-variation architecture; a service target of the TINA-variationarchitecture is an enterprise data center; the TINA-variationarchitecture includes an Access Session Layer, a Service Session Layer,a Resource Session Layer, and a Provision Session Layer; theTINA-variation architecture is left-right asymmetrical; physicalresources of the TINA-variation architecture include IT resources,storage resources, and network resources; the service delivery platformis used by a project developer, a project operator, an application user,and a system operator; wherein the service delivery platform includes aProject Delivery Service Network, a Project Logical Environment ServiceNetwork, a Project Logical Environment Storage Network, a ProjectLogical Environment Resource Network, a Virtual Resource Network, and aData Center Physical Resource Service Network Divided by Project; theProject Delivery Service Network includes a Project Core Service, aProject Design Service, a Project Delivery Scheduling, and a ProjectSubscription Service; the Project Logical Environment Service Networkincludes multiple sets of offline-projects' and online-projects' logicalpoint-of-delivery, in which the project-delivery-and-scheduling functionsupports automatic or manual offline-online environment switching, andsupports scheduling multiple sets of projects' point-of-delivery; theProject Logical Environment Storage Network includes multiple sets ofoffline-project instances' point-of-delivery; the Project LogicalEnvironment Resource Network includes multiple sets of online-projectinstances' point-of-delivery; the Virtual Resource Network in whichvirtual resources aggregate physical resources of differentconfigurations and different locations, is configured to achieveresource consolidation regardless of type and deployment of the physicalresources; wherein the virtual resource network includes unallocated andallocated virtual resources and the Virtual Resource Network providessupport of exclusive holding or sharing virtual resources; the DataCenter Physical Resource Service Network Divided by Project includesmultiple sets of physical point-of-delivery; the Data Center PhysicalResource Service Network Divided by Project supports subscription andcommitment of the point-of-delivery, and supports sharing physicalresources by space or by time; and the Data Center Physical ResourceService Network Divided by Project includes unallocated and allocatedphysical resources; wherein the Resource Session Layer includes aresource session related component: a Resource Session Manager; whereinthe Resource Session Manager manages end-to-end resource provision,provides an interface which allows the User Service Session Manager, theOperator Service Session Manager Session Manager to create, modify, anddelete end-to-end resource provision.